[SPARK-35433][DOCS] Move CSV data source options from Python and Scala into a single page#32658
[SPARK-35433][DOCS] Move CSV data source options from Python and Scala into a single page#32658itholic wants to merge 5 commits intoapache:masterfrom itholic:SPARK-35433
Conversation
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Test build #138912 has finished for PR 32658 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #138974 has finished for PR 32658 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Test build #139003 has finished for PR 32658 at commit
|
|
Test build #139005 has finished for PR 32658 at commit
|
|
Kubernetes integration test status success |
|
Kubernetes integration test status success |
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Kubernetes integration test status failure |
|
Test build #139042 has finished for PR 32658 at commit
|
|
Test build #139044 has finished for PR 32658 at commit
|
Thanks, @HyukjinKwon . Just fixed them in every place. |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #139093 has finished for PR 32658 at commit
|
|
Merged to master. |
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Test build #139126 has finished for PR 32658 at commit
|

What changes were proposed in this pull request?
This PR proposes move CSV data source options from Python, Scala and Java into a single page.
Why are the changes needed?
So far, the documentation for CSV data source options is separated into different pages for each language API documents. However, this makes managing many options inconvenient, so it is efficient to manage all options in a single page and provide a link to that page in the API of each language.
Does this PR introduce any user-facing change?
Yes, the documents will be shown below after this change:
How was this patch tested?
Manually build docs and confirm the page.